Uh oh, reflection = danger zone. We're bypassing a lot of compilation-time guarantees.

What's the problem we're trying to solve here?

Do skipped actions malform the ActionMetric.label proportions too much? Our initial workaround was to run the test for a longer time so they get averaged out.
If that is not effective enough, then we can avoid action skips by using a self-loading Memory, e.g. pass this to an action during Memory.recall:

fun recall(): String {
    if (issueKeys.isEmpty()) {
        SearchJqlAction(jira, throwawayActionMeter, IssueJqlMemory(), this).run()
    }
}

This way you can avoid skips with local logic rather than a global order-controlling scheme.

Yes. I want to preserve the requested proportions. During our runs, ~1500 view issue calls are skipped. This looks like a minimally invasive way of achieving this, without altering the way scenarios are created.
The problem with hiding the query inside a different action is that you lose control over proportions - if there are permission issues, the JQL action can be executed as often as view issue, which we don't want. If we stick to sorting, everything is transparent and there are no surprises hiding in the implicit initialisation.

The same problem affects ViewBoard, btw.

Let's try a different question: is there any benefit to keeping a fully-randomised shuffle in the scenario?

🤔
I'll come back to this next week